The system has several internal scheduled events that are run in the background.
- Use the Task Manager to see a listing of all system tasks in a single listing.
AD sync time interval
The AD sync time interval determines how frequently to sync Pyramid users with AD users and groups. Setting this too frequently can negatively impact both Pyramid and the AD. If you set the sync interval to 8 hours or more, you will see additional options to set the start time:
- Start Hour: set the start time for the sync interval.
- Timezone: set the timezone for the sync interval.
Log Cleaner time interval
This timer determines how frequently to clean the various logs in the system using the "auto-purge" settings from the logging page. Logs can be cleaned at an interval of 2 days, 1 day, or 12 hours
Note that this does not affect how long the system logs are kept. For example:
- If you've chosen to keep system logs for 1 month (in Logging), and then you set the Log cleaner time interval to 1 day:
- The logs will be kept for 1 month
- After the initial 1 month, 1 day of logs will be cleaned every day, i.e., first day of the second month, the logs from the first day of the first month will be cleaned
- This means there will always be 1 month's worth of logs
Personalization time interval
The Content Explorer includes a features called "Recommended" which uses a special machine learning based engine to recommend content items that a user is likely to find interesting based on what others in the system have used.
Set the Personalization time interval to determine how frequently these algorithms should be re-calibrated and run. Unless there is a huge variety of users making different choices very regularly, changes to the engines models will not be impacted by running this too regularly.
Snapshots time interval
The system creates image snapshots of content to provide convenient graphic icons of the items for the content explorer tools.
Set the Snapshots time interval to determine how frequently Pyramid should create these snapshots in the background. The system will only create snapshots for new content items, or content items that have been changed.
Processed Tasks
The system manages all generated outputs and processing logs. Set the amount of time to keep the content and associated logs in the system before they are auto-purged. It is good practice to purge older items since they are not useful unless needed for ongoing diagnosis.
- Time to keep Alert Outputs: Sets the amount of time to maintain the information that was created as a result of the Alert Outputs that the system created.
- Time to keep Model processing logs: Sets the amount of time to keep the Model processing logs in the system.
- Time to Keep Rendered Content: Sets the amount of time to keep rendered content including printing, publications, and subscriptions.
Log Purge
The purge settings determine how long each log is kept on the system before being purged. It is good practice to purge logs regularly to keep the repository database operating efficiently. Click Run Now to immediately purge the logs according to the time selected.
Schedule default
Set up system default values for scheduled jobs. These values are used when you select System Default as the value in your schedule handling settings for Advanced Alerts, Model Scheduling, Publishing, and in the Alerts and Subscription managers.
- Schedule timeout: Disables the scheduled task after this amount of time. Selecting None means that the job will run without ever aborting.
- Disable schedule after consecutive failure: Disables the scheduled task after this number of attempts is reached. Once a job has failed more than this number of times, it is canceled and will only run if it is manually restarted. Selecting Never disable means that the job will continue to retry regardless of the number of failures.
Note: The defaults that are used out-of-the-box for these values are: (1) a four-hour timeout and (2) three consecutive failures before the job is disabled.